home
***
CD-ROM
|
disk
|
FTP
|
other
***
search
/
SGI Performance Co-Pilot 1.3
/
SGI Performance Co-Pilot 1.3.iso
/
dist
/
pcp.idb
/
usr
/
share
/
catman
/
u_man
/
cat1
/
pmdumplog.z
/
pmdumplog
Wrap
Text File
|
1997-04-03
|
6KB
|
133 lines
PPPPMMMMDDDDUUUUMMMMPPPPLLLLOOOOGGGG((((1111)))) PPPPMMMMDDDDUUUUMMMMPPPPLLLLOOOOGGGG((((1111))))
NNNNAAAAMMMMEEEE
ppppmmmmdddduuuummmmpppplllloooogggg - dump internal details of a performance metrics archive log
SSSSYYYYNNNNOOOOPPPPSSSSIIIISSSS
ppppmmmmdddduuuummmmpppplllloooogggg [----aaaaddddiiiillllmmmmrrrrttttzzzz] [----nnnn _n_a_m_e_s_p_a_c_e] [----ZZZZ _t_i_m_e_z_o_n_e] _a_r_c_h_i_v_e [_m_e_t_r_i_c_n_a_m_e
...]
ppppmmmmdddduuuummmmpppplllloooogggg [----vvvv _f_i_l_e]
DDDDEEEESSSSCCCCRRRRIIIIPPPPTTTTIIIIOOOONNNN
ppppmmmmdddduuuummmmpppplllloooogggg dumps assorted control, metadata, index and state information
from the files of a Performance Co-Pilot (PCP) archive log. The archive
log has the base name _a_r_c_h_i_v_e and must have been previously created using
ppppmmmmllllooooggggggggeeeerrrr(1).
Normally ppppmmmmdddduuuummmmpppplllloooogggg operates on the default Performance Metrics Namespace
(PMNS), however if the ----nnnn option is specified an alternative namespace is
loaded from the file _n_a_m_e_s_p_a_c_e.
If any _m_e_t_r_i_c_n_a_m_e arguments appear, the report will be restricted to
information relevant to the named performance metrics.
The options control the specific information to be reported.
----aaaa Report everything.
----dddd Display the metadata and descriptions for those performance metrics
that appear at least once in the archive: see ppppmmmmLLLLooooooookkkkuuuuppppDDDDeeeesssscccc(3) for
more details on the metadata describing metrics.
----iiii Display the instance domains, and any variations in their instance
members over the duration of the archive: see ppppmmmmGGGGeeeettttIIIInnnnDDDDoooommmm(3) for more
details on instance domains.
----llll Dump the archive label, showing the log format version, the time and
date for the start and (current) end of the archive, and the host
from which the performance metrics values were collected.
----mmmm Print the values for the performance metrics from the archive. This
is the default display option.
----rrrr Process the archive in reverse order, from most recent to oldest
recorded metric values.
----tttt Dump the temporal index that is used to provide accelerated access
to large archive files.
----vvvv Verbose mode. Dump the records from a physical archive file in
hexadecimal format. In this case _f_i_l_e is the name of a single file,
usually a basename (as would otherwise appear as the _a_r_c_h_i_v_e command
line argument), concatenated with ``.'' followed by one of mmmmeeeettttaaaa (the
metadata), iiiinnnnddddeeeexxxx (the temporal index), or a digit (one of the
volumes of metric values).
PPPPaaaaggggeeee 1111
PPPPMMMMDDDDUUUUMMMMPPPPLLLLOOOOGGGG((((1111)))) PPPPMMMMDDDDUUUUMMMMPPPPLLLLOOOOGGGG((((1111))))
Use of ----vvvv precludes the use of all other options and arguments.
By default, ppppmmmmdddduuuummmmpppplllloooogggg reports the time of day according to the local
timezone on the system where ppppmmmmdddduuuummmmpppplllloooogggg is run. The ----ZZZZ option changes the
timezone to _t_i_m_e_z_o_n_e in the format of the environment variable TTTTZZZZ as
described in eeeennnnvvvviiiirrrroooonnnn(5). The ----zzzz option changes the timezone to the local
timezone at the host that is the source of the performance metrics, as
specified in the label record of the archive log.
FFFFIIIILLLLEEEESSSS
////vvvvaaaarrrr////ppppccccpppp////ppppmmmmnnnnssss////* default PMNS specification files
////vvvvaaaarrrr////aaaaddddmmmm////ppppccccpppplllloooogggg////_h_o_s_t_n_a_m_e
Default directory for PCP archives containing
performance metric values collected from the host
_h_o_s_t_n_a_m_e.
SSSSEEEEEEEE AAAALLLLSSSSOOOO
ccccrrrroooonnnn....ppppmmmmcccchhhheeeecccckkkk(1), ccccrrrroooonnnn....ppppmmmmddddaaaaiiiillllyyyy(1), ppppmmmmllllooooggggggggeeeerrrr(1), ppppmmmmllllooooggggmmmmeeeerrrrggggeeee(1), PPPPMMMMAAAAPPPPIIII(3),
ppppmmmmGGGGeeeettttIIIInnnnDDDDoooommmm(3) and ppppmmmmLLLLooooooookkkkuuuuppppDDDDeeeesssscccc(3).
DDDDIIIIAAAAGGGGNNNNOOOOSSSSTTTTIIIICCCCSSSS
Mostly self evident, given the likely need to be using ppppmmmmdddduuuummmmpppplllloooogggg.
PPPPaaaaggggeeee 2222